The fixture crm_resources is auto use fixture, in it, it will check the crm resources, the timeout of checking the crm resource is 90s, if there is a config reload did before the test, and since the default crm polling interval is 360s, so the 90s timeout is not enough, actually, there is another auto use fixture set_polling_interval which is also module level, in it, the crm polling interval will be changed to 1s, but it is called after the crm_resources, change the set_polling_interval always called before the crm_resources, then even if there is config reload did before this test, 90s timeout is enough to get the crm resources.

<!--
Please make sure you've read and understood our contributing guidelines;
https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md

Please provide following information to help code review process a bit easier:
-->
### Description of PR
<!--
- Please include a summary of the change and which issue is fixed.
- Please also include relevant motivation and context. Where should reviewer start? background context?
- List any dependencies that are required for this change.
-->

Summary: The fixture crm_resources  is new added in sonic-net/sonic-mgmt#18465.
Fixes # (issue)

### Type of change

<!--
- Fill x for your type of change.
- e.g.
- [x] Bug fix
-->

- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
    - [ ] Skipped for non-supported platforms
- [x] Test case improvement

### Back port request
- [ ] 202205
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [x] 202505

### Approach
#### What is the motivation for this PR?

#### How did you do it?

#### How did you verify/test it?

#### Any platform specific information?

#### Supported testbed topology if it's a new test case?

### Documentation
<!--
(If it's a new feature, new test case)
Did you update documentation/Wiki relevant to your implementation?
Link to the wiki page?
-->